-
Notifications
You must be signed in to change notification settings - Fork 7
docs: rename Starter tools to Unoptimized #721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Style Review
Found 4 style suggestion(s).
Powered by Vale + Claude
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
| - Optimized tools | ||
|
|
||
| The distinction is merely a matter of how they are designed. Both types of tools can be used seamlessly in the same way. There is no difference in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/references). | ||
| The distinction is merely a matter of how Arcade designs them. Both types of tools can be used seamlessly in the same way. No difference exists in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/references). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how Arcade designs them
This was a vale suggestion, but I think we have some community contributions so this isn't quite true always? Except maybe it is because the Optimized ones are optimized by us?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good discussion to have now. The community toolkits was an idea where we would show non-arcade toolkits in our docs, kind of like a marketplace. We are not doing that, and with MCP servers, I think we will not do it in the short term, so I'm not sure if it's valid to keep that category.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, cool, then I don't think this suggestion is an issue :)
| Since they require careful design and evaluation, Optimized tools take time and effort to build. Arcade understands that your Agent or chatbot project might need capabilities not yet covered by Arcade's Optimized MCP Servers. For this reason, Arcade also offers low-level Unoptimized MCP Servers (formerly known as Starter MCP Servers). | ||
|
|
||
| ## Starter tools | ||
| <span id="starter-tools" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a weird suggestion from Cursor to not break existing links. It's clever I guess, but I'm not sure it's right.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ummm, I don't get why there is an empty span here.
| **Toolkits** | ||
|
|
||
| - `[feature - 🚀]` Introduce [Starter Tools](/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service. | ||
| - `[feature - 🚀]` Introduce [Unoptimized tools](/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want to back-edit the changelog...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Umm, I think it's ok.
app/en/resources/glossary/page.mdx
Outdated
|
|
||
| #### Starter tools | ||
| <span id="starter-tools" /> | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
again with clever link stuff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link is generated automatically by Nextra for markdown titles. I don't understand this span.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cursoragent please remove the empty spans added here and elsewhere in this PR's diff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update: empty spans removed
- Removed the empty
<span id="starter-tools" />elements from:app/en/guides/create-tools/improve/types-of-tools/page.mdxapp/en/resources/glossary/page.mdx
- Committed and pushed the fix to
plt-1035-unoptimized-terminology(docs: remove empty span anchors). - Verified by running
pnpm test(all link/docs tests passed).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I think it was so the browser can still anchor to the old link? But I also think it was cursor being too clever.)
|
@nearestnabors this PR is blocked on the monorepo updates, but the content is worthy of a review in the meantime |
sdserranog
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nits, but this is good to go. ![]()
Co-authored-by: Teal Larson <LARSON.TEAL@GMAIL.COM>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| before using it in production.{" "} | ||
| <a href="/guides/create-tools/improve/types-of-tools">Read more</a> about | ||
| Optimized vs Starter tools. | ||
| Optimized vs Unoptimized tools. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Component name inconsistent with displayed content
Low Severity
The component StarterToolInfo and file starter-tool-info.tsx now display content about "Unoptimized MCP Server" and "Unoptimized tools", creating a naming mismatch. This component is imported across 8+ pages in the codebase. Developers searching for "unoptimized" related code won't find this file. Consider renaming to UnoptimizedToolInfo or similar for consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is acceptable for now. I didn't want to introduce a bigger diff, and we still refer to them in code as starter in some places as well. The "optimized" term is just a user-facing change.




Contains docs updates that align with the changes in the toolkit picker here and here.
This should ideally not be merged until approximately when those changes go live.
Note
Low Risk
Primarily copy/link updates with minimal code impact; main risk is broken navigation if any updated anchors/URLs are incorrect.
Overview
Renames the “Starter” tool type to “Unoptimized” across the docs site, including the
Types of Toolsguide, glossary, changelog entry, and the starter-tool warning callout.Updates toolkit picker/filter UI strings (
type-config.tsx,use-toolkit-filters.ts) to display “Arcade Unoptimized” / “Arcade Unoptimized MCP Server” and repoints related doc links to the new#unoptimized-toolsanchor; also refreshespublic/llms.txtto reflect the new terminology.Written by Cursor Bugbot for commit 45ba4c0. This will update automatically on new commits. Configure here.